home *** CD-ROM | disk | FTP | other *** search
- Subject: Re: Linking & ODF Draw
- Sent: 6/3/96 7:37 AM
- Received: 6/3/96 11:51 AM
- From: Scott, scottdfl@sprynet.com
- Reply-To: ODF Interest, ODF-Interest@CILabs.ORG
- To: OpenDoc Development Framework Discussion List, ODF-Interest@CILabs.
-
- Mary,
-
- Thanks for the timely response. I really appreciate it since I am on
- a rather tight schedule, and ODF R1 is a big change from D11.
- However, I am still totally confused.
-
- You said,
-
- > When a part or selection is externalized, the shapes are numbered from 1 to n.
- >Then when the part or selection is internalized, these indices are used by the linking
- >internalization code to identify
- > the shapes involved in links. After internalization
- >the indices don't matter anymore. If the part/selection is externalized again, new
- >indices are assigned.
- >
- > So, basically, the shape indices are only valid in the context of a particular
- > ODFDraw storage unit.
- >
- > Mary Boetcher
- > ODF Person
- >
-
-
- I understand what you are saying, but that still doesn't make sense
- of the ODF Draw code. It appears that the indices are assigned when
- the part is internalized from storage, via "PostInternalizeShape",
- ditto for the selection. So, if I create a new document, draw some
- shapes, save the doc, and reopen it, the shapes will be numbered
- 1..n. Then I paste some more shapes, now my doc's shape list is
- numbered 1..n, 1..m. Now I select some shapes (including some that I
- just pasted in). Let's say I have 8 shapes altogether, numbered 1..5,
- 1..3, and I select the first, third and last shape. When I copy, the
- selection is externalized with the shape indices of 1, 3 & 3.
-
- Is this sound right? If not, then what am I missing? I have traced
- thru the ODF Draw code as best as I can, and have read the ODF user
- guide. Some constructive criticism for future documentation would be
- to explain what is going on rather than just give examples, but you
- are probably already headed that direction. Also, what really
- confuses me is that ODF Draw uses the same content base class for
- both its part storage as well as its selection, but in my case (and
- maybe others as well) that is not a workable model. It also makes the
- code harder to understand since when one is in some overriddem member
- function, it isn't obvious which shape list is being used.
-
- Thanks again for the timely help.
-
-
-
- Scott Daniels
- e-mail: scottdfl@sprynet.com
- "Life appears the way you choose to see it"
-